Your Render PR Server URL is https://pmm-doc-pr-1159.onrender.com.

Follow its progress at https://dashboard.render.com/static/srv-ckfs96ol3its7382c4e0.

I love the improvements! A few comments after having a quick look:

1. I would change "Install PMM" headline to "Install PMM Server"
2. I would change "Once PMM is set up, choose the database that you want it to monitor:" to "Once PMM Server is set up, choose the service that you want it to monitor" (technically, we also monitor ProxySQL and HAProxy which are not DBs
3. Installing PMM package step in each tech would benefit from having two tabs - with Debian and RHEL commands (apt-get vs yum).
4. "Install Percona Release Tool" should be linked ti its documentation
5. "Alternative database connection workflows" tab has "PMM Client installation via User Interface" link. I think it would be better to rename it to "Adding remote instance via User Interface" (because technically it does not install PMM Client anywhere)
6. Postgres instructions are incomplete. They miss steps required to enable pg_stat_monitor.
7. Step 2 of POstgres instructions are too long. I don't think all the explanation what pg_stat_monitor is is required.

1. I would change "Install PMM" headline to "Install PMM Server"
   This was intentional (my ask) to keep users from overloading about Client-server and options.
   As the main action they expect - is "install PMM," not "some pmm components,"

2. I would change "Once PMM is set up, choose the database that you want it to monitor:" to "Once PMM Server is set up, choose the service that you want it to monitor" (technically, we also monitor ProxySQL and HAProxy which are not DBs

Perhaps we should label it as "Database or Application" instead. Terms like Services and Nodes are internal jargon, and using PMM is the best way to get familiar with them. Our goal is to use language that is easily understandable to users in our initial interactions.

Will all other suggestions - 👍